Skip to content

fix: change artifactId for java client#865

Merged
Deflaimun merged 1 commit intokurrent-io:masterfrom
nvcc1701:master
Apr 18, 2025
Merged

fix: change artifactId for java client#865
Deflaimun merged 1 commit intokurrent-io:masterfrom
nvcc1701:master

Conversation

@nvcc1701
Copy link
Copy Markdown
Contributor

This PR addresses wrong arti factIdissues that occurred during the rebranding from "Event Store" to "Kurrent". The main issue was incorrect article usage - using "db-client-java" instead of "kurrentdb-client" .

Description

  • Fixed article usage in multiple documentation files
  • Corrected instances of "db-client-java" to "kurrentdb-client"

Page previews

@nvcc1701 nvcc1701 requested a review from a team as a code owner April 18, 2025 11:59
@CLAassistant
Copy link
Copy Markdown

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.


anh nguyen seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
You have signed the CLA already but the status is still pending? Let us recheck it.

@nvcc1701 nvcc1701 closed this Apr 18, 2025
@Deflaimun
Copy link
Copy Markdown
Contributor

Hi ! Thank you for your contribution. Let me take over this PR and implement it on our docs

@Deflaimun Deflaimun reopened this Apr 18, 2025
@Deflaimun Deflaimun merged commit 98cdbb3 into kurrent-io:master Apr 18, 2025
1 of 2 checks passed
Deflaimun added a commit that referenced this pull request Apr 18, 2025
Event Store -> Kurrent

EventStoreDB -> KurrentDB

kurrent link

update docker image

org name

revert past v24 names

revert changes to deprecated client

revert some pages where EventStoreDB made more sense giving the versioning

revert

rebrand clients

update go version

add python and go

docs: Rebrand from EventStore to Kurrent (#828)

Co-authored-by: Mark Morrissey <90937442+coloradomorrissey@users.noreply.github.com>
Co-authored-by: Hayley Campbell <hayleyjeancampbell@gmail.com>

engine: captures 404 page events (#859)

engine: modify toc with feedback behavior (#863)

engine: additional fix for the toc (#864)

docs: change artifactId for java client (#865)

Co-authored-by: anh nguyen <nvcc1701@gmail.com>
Deflaimun added a commit that referenced this pull request Apr 18, 2025
Event Store -> Kurrent

EventStoreDB -> KurrentDB

kurrent link

update docker image

org name

revert past v24 names

revert changes to deprecated client

revert some pages where EventStoreDB made more sense giving the versioning

revert

rebrand clients

update go version

add python and go

docs: Rebrand from EventStore to Kurrent (#828)

Co-authored-by: Mark Morrissey <90937442+coloradomorrissey@users.noreply.github.com>
Co-authored-by: Hayley Campbell <hayleyjeancampbell@gmail.com>

engine: captures 404 page events (#859)

engine: modify toc with feedback behavior (#863)

engine: additional fix for the toc (#864)

docs: change artifactId for java client (#865)

Co-authored-by: anh nguyen <nvcc1701@gmail.com>
Deflaimun added a commit that referenced this pull request Apr 18, 2025
Event Store -> Kurrent

EventStoreDB -> KurrentDB

kurrent link

update docker image

org name

revert past v24 names

revert changes to deprecated client

revert some pages where EventStoreDB made more sense giving the versioning

revert

rebrand clients

update go version

add python and go

docs: Rebrand from EventStore to Kurrent (#828)

Co-authored-by: Mark Morrissey <90937442+coloradomorrissey@users.noreply.github.com>
Co-authored-by: Hayley Campbell <hayleyjeancampbell@gmail.com>

engine: captures 404 page events (#859)

engine: modify toc with feedback behavior (#863)

engine: additional fix for the toc (#864)

docs: change artifactId for java client (#865)

Co-authored-by: anh nguyen <nvcc1701@gmail.com>
@Deflaimun
Copy link
Copy Markdown
Contributor

hey @nvcc1701. Just out of curiosity. Why did you close the PR? Was it because the CLA signature?

@nvcc1701
Copy link
Copy Markdown
Contributor Author

nvcc1701 commented Apr 23, 2025

hi, im new to contribution, i just not sure do i follow the contribution rules. so i close the mr, and i think i will create new mr, but i see it merged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants